home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
network
/
tech3.zip
/
TECH.DOC
< prev
Wrap
Text File
|
1990-06-13
|
49KB
|
1,541 lines
LANtastic (tm) Network Operating System
Technical Reference Manual
=================================================
Introduction
************
This manual is intended for programer who wish to make use of the
network services of the LANtastic Network Operating System (LANOS).
LANOS services described in this manual are for version 3.00 or above.
LANOS services fall into two catagories: Standard MS-DOS compatible
network functions and Extended network functions. Since LANOS runs
on any NETBIOS compatible LAN, NETBIOS functions are also available
although they are intrisic to the underlying NETBIOS implementation.
This manual assumes that the reader is familiar with 8088/8xx6
assembly language and DOS system functions. Since the standard
MS-DOS compatible network functions are described in the DOS
technical reference manual, we will not go into great detail in this
manual.
Throughout this manual references will be made to network paths.
LANOS network paths are fully compatibly with MS-DOS network paths.
Network paths are similar to file paths except that they reference
files through the network. The general syntax for network path is
\\server-name\path-name
where
server-name is 1 to 15 character name of a network file server
path-name is a DOS path on the server
For example,
\\MAIN-MACHINE\PROGS\DATA\FROG.TXT
refers to a file located on server MAIN-MACHINE. The path required
to access the file is PROGS\DATA\FROG.TXT. The directory PROGS is a
shared network directory and may not actually exist on the server. It
may in fact be an entire disk.
MS-NET compatible networks (e.g. IBM-PC LAN) do not fully support
full paths for all systems calls (in particular Find FIrst). LANOS,
however, supports full paths for all system calls that can take a
path argument. This means that many public domain directory
utilities will operate with a network path. Refer to the "Other
useful system calls" section for example uses of find-first/next.
Indirect Files
**************
As of version 3.00 of LANOS, a new type of file has been created for
use on the network. This file type, know as an indirect file,
resides on a server and is accessable to all users with the 'I' ACL
privilege. An indirect file contains server relative path
information that is expanded in place of the file's name when a path
is parsed by the server. In other words, an indirect file points to
another file or directory. Whenever you refer to the indirect file,
its name is replaced by the file or directry it refers to.
The folowing examples illustrate the operation of indirect files.
Given the following indirect files
Indirect file Contents
------------------- ---------------------
\ROOT\A \ROOT\AUTOEXEC.BAT
\MISC\C \ROOT\CONFIG.SYS
\ROOT\SOURCES\WIN.H ..\INCLUDE\WINDOW.H
\ROOT\DOC \MISC\MANUALS\NEW\DOC
Some sample path expansions would be
Path Expansion
-------------------- --------------------------------
\ROOT\A \ROOT\AUTOEXEC.BAT
\MISC\C \ROOT\CONFIG.SYS
\ROOT\SOURCES\WIN.H \ROOT\INCLUDE\WINDOW.H
\ROOT\DOC\INTRO \MISC\MANUALS\NEW\DOC\INTRO
\ROOT\DOC\CHAPTERS\1 \MISC\MANUALS\NEW\DOC\CHAPTERS\1
As you can see from the above examples, indirect files can be used to
point to other files or directories. The advantage of indirect files
is that the actual files or directories that they point to can reside
on one area while multiple indirect file can reference them with a
variety of names while residing in another directory.
Since the concept of indirect files does not exists under DOS.
Indirect files are not available directly from DOS. To use indirect
files you must reference them through the network.
System calls that are useful for the manipulation of indirect files
are
5FB3H Translate path
5FB4H Create indirect file
5FB5H Get indirect file contents
Error Codes
***********
All MS-DOS compatible system calls and all LANOS specific system calls
return error codes. The error code number is always returned in AX.
When an error occurs the carry flag (CY) is set. LANOS provides a
mechanism for expanding the error code number into a text string. The
following is a list of error codes which may be returned by LANOS:
Error
Number Meaning
------ -------
01H Invalid function number
02H File not found
03H Path not found
04H File open limit has been exceeded or no handles left
05H Access denied
06H Invalid handle
07H Memory control blocks destroyed
08H The memory limit has been exceeded
09H Invalid memory block address
0AH Invalid environment
0BH Invalid format
0CH Invalid access code
0DH Invalid data
0EH RESERVED
0FH Invalid drive was specified
10H Attempt to remove current directory
11H Not same device
12H No more files
13H Attempt to write on write protected disk
14H Unknown unit
15H Drive not ready
16H Unknown command
17H Data CRC error
18H Bad req stuc length
19H Seek error
1AH Unknown media
1BH Sector not found
1CH No paper
1DH Write fault
1EH Read fault
1FH General failure
20H Sharing violation
21H Lock violation
22H Invalid disk change
23H FCB unavailable
24H Sharing buffer overflow
25H RESERVED
26H Cannot complete file operation
27H-31H RESERVED
32H Network request not supported
33H Network node ??????????????? is not listening
34H The name already exists on the network
35H Cannot locate network name
36H The network is busy
37H Server connection to network node ??????????????? broken
38H The NETBIOS command limit has been exceeded
39H The network adapter has malfunctioned
3AH Incorrect response received from network node ???????????????
3BH Unexpected network error from network node ???????????????
3CH Incompatible network node ???????????????
3DH Print queue full on network node ???????????????
3EH No room for print file on network node ???????????????
3FH The print file has been deleted on network node ???????????????
40H The network name has been deleted
41H You have been denied access on network node ???????????????
42H Invalid network device
43H The network name was not found
44H The network name limit has been exceeded
45H The session limit has been exceeded
46H Network node ? has been temporarily paused
47H The network request to network node ? was denied
48H Print or disk redirection is paused on network node ???????????????
49H Invalid network version
4AH Account has expired
4BH Password has expired
4CH Login attempt invalid at this time
4DH Disk limit has been exceeded on network node ???????????????
4EH Not logged in to network node ???????????????
4FH RESERVED
50H The file already exists
51H RESERVED
52H Cannot make directory entry
53H Failure on critical error
54H Too many redirections or logins to network node ???????????????
55H Duplicate redirection or login to network node ???????????????
56H Invalid username or password
57H Invalid parameter
58H Network data fault
59H Function not supported on network
5AH Required system component not installed
When you expand the error code into a text string the above question
marks are expanded to the name of the node you were refering to. To
expand an error code into a text string you will need to issue a
multiplex interrupt (2FH). The calling sequence is
INPUT AH 5
AL 0 For installation check
# for error code (in pre DOS 4.00)
1 or 2 for error code in DOS 4.00
BX in Error code
OUTPUT FLAGS NC if error code converted to text
CY is error code can't be converted
ES:DI Pointer to ASCIZ text buffer containing error text.
This is a read only text buffer and you must not alter
the text in this buffer.
If the error code is RESERVED it is expanded to "General failure". The
maximum width for the question mark fields is 15 characters. The error
text is automatically adjusted so that extra spaces are not in the text
buffer. For example the error text
Network node ??????????????? is not listening
would be
Network node HOST is not listening
for node HOST.
When coding for LANOS the following code se